Fix .vsconfig #56339
Merged
Fix .vsconfig #56339
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
PR validation is messed up. but this file is not used in build or tests. |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Importing the .vsconfig in our repo was causing VS to install an older CRT. We need the newer one to avoid
https://developercommunity.visualstudio.com/t/vs2019-lnk2046-and-lnk2047-reported-when-static-li/1306948
thanks @janvorli for the clue
Mostly moves are caused by VS. I left them in the hope there is some opaque stable sort behind them. Also removed the old targeting packs that VS2022 doesn't support.
Verified both are ingested by VS2019 and VS2022 happily.